-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: augment tokenID to token vending machine #978
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the small change in the readme
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Addressed in a commit not sure why it doesnt mark as addressed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one nit, not necessarily a blocker
|
||
You can also pass a tokenId as a query string to your curl command to add context to your token. This can be particularly useful when using [Momento Topics](https://www.gomomento.com/services/topics) as the tokenId can be retrieved from subscription messages, allowing your application to distinguish between different subscribers. | ||
|
||
`https://9jkmukxn68.execute-api.us-west-2.amazonaws.com/prod?name=Taylor` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we be consistent in the name of the query param and what you say in the docs? you say tokenId
and then the QP is name
. kinda seems like the most clear thing to do is just have the QP be named tokenId
as well. just a nit though, i don't feel too strongly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll clarify that in this case the tokenId
is the name. Good call out. The reason I want it to be more relatable to the real world is for customers to be able to derive some sense of the use case
Added
tokenId
to TVM examples. I have demonstrated this as a query string parameter as a generictokenId
was not making sense but let me know if there's a better way to demonstrate this.